ref: Differentiate between memory and file cache keys #1487
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This passes two different cache keys (
memory_cache_key
andfile_cache_key
) to thecompute_memoized
method. The intended use case comes from proguard processing: we want to keep proguard files on disk as a whole, but only load segments of them into memory at a time. To this end, we want several in-memory cache keys (those of the individual parts of the proguard file) to correspond to one on-disk cache key (that of the entire file).